Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1748

reference
869-tree-1
name
1748
tree-preservation-order

undefined

869-tpo-1
uprn
address-text
point
POINT (-1.038781 50.870619)
geometry
MULTIPOLYGON (((-1.038653 50.870606,-1.038659 50.870631,-1.038676 50.870654,-1.038704 50.870672,-1.038740 50.870684,-1.038779 50.870688,-1.038819 50.870684,-1.038855 50.870673,-1.038883 50.870655,-1.038902 50.870633,-1.038909 50.870608,-1.038903 50.870583,-1.038885 50.870560,-1.038857 50.870542,-1.038822 50.870530,-1.038782 50.870526,-1.038743 50.870530,-1.038707 50.870541,-1.038678 50.870558,-1.038660 50.870581,-1.038653 50.870606)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL